HOSPITAL
The framework is the same for every building. This is where the hospital gets its own design process.
What the client usually gives
"We need a 500-bed hospital."
Most of the time that one number is the whole brief. Everything else starts as Assumed, and the system has to fill it in before any design can begin.
- Number of beds
- The plot and its papers
- Location, which picks the rule pack
- How the beds split: wards, ICU, private rooms
- How many operation theatres
- How busy the OPD will be
- Size of emergency
- Services: kitchen, laundry, CSSD, stores
- Phasing
Default values the system assumes
When the brief stops at "500 beds", these defaults fill the gap. Each one stays tagged Assumed until the client confirms it.
| Department | Share | Tag |
|---|---|---|
| IPD wards | to fill | Assumed |
| OPD | to fill | Assumed |
| Operation theatres | to fill | Assumed |
| ICU | to fill | Assumed |
| Diagnostics and imaging | to fill | Assumed |
| Emergency | to fill | Assumed |
| Services and support | to fill | Assumed |
| Admin | to fill | Assumed |
| Circulation | to fill | Assumed |
| Item | Per 100 beds | Tag |
|---|---|---|
| Operation theatres | to fill | Assumed |
| ICU beds | to fill | Assumed |
| OPD consult rooms | to fill | Assumed |
| Emergency beds | to fill | Assumed |
I am filling these from IPHS (MoHFW) and real project data. Until a value is checked it stays empty here. An empty box is more honest than a made-up number.
The programme those defaults produce
Change the numbers and the programme follows. The parts that use verified rules already work. The department split joins in once its values are filled.
Each row turns into an area as soon as its share is filled in the hospital module.
Plugin status
- Hospital module JSON v0.1Done
- Department defaultsTo fill
- Programme generatorPlanned
- Hospital design plugin (Grasshopper)Planned